Skip to content

Conversation

@khluu
Copy link
Contributor

@khluu khluu commented Oct 8, 2025

So it can be configured for expensive tests to not retry

p
Signed-off-by: kevin <[email protected]>
@khluu khluu requested a review from a team as a code owner October 8, 2025 23:13
@khluu
Copy link
Contributor Author

khluu commented Oct 8, 2025

cursor[bot]

This comment was marked as outdated.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a useful feature to configure the number of retries for release tests. The implementation is straightforward, but I've found one important issue in the logic that handles the num_retries value. Please see my comment below.

cmd += ["--smoke-test"]

num_retries = test.get("run", {}).get("num_retries")
if num_retries:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The condition if num_retries: will evaluate to False when num_retries is 0. This prevents disabling retries for a test by setting num_retries: 0, which is a key use case mentioned in the PR description ("to not retry"). When num_retries is 0, the default retry limit (likely 1) will be used instead of disabling retries.

To correctly handle the case where num_retries is 0, you should check if the value is not None.

Suggested change
if num_retries:
if num_retries is not None:

@khluu khluu requested a review from aslonnie October 8, 2025 23:16
if smoke_test:
cmd += ["--smoke-test"]

num_retries = test.get("run", {}).get("num_retries")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unit test?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done!

@ray-gardener ray-gardener bot added core Issues that should be addressed in Ray Core devprod release-test release test labels Oct 9, 2025
@github-actions
Copy link

This pull request has been automatically marked as stale because it has not had
any activity for 14 days. It will be closed in another 14 days if no further activity occurs.
Thank you for your contributions.

You can always ask for help on our discussion forum or Ray's public slack channel.

If you'd like to keep this open, just leave any comment, and the stale label will be removed.

@github-actions github-actions bot added the stale The issue is stale. It will be closed within 7 days unless there are further conversation label Oct 23, 2025
@khluu khluu requested a review from aslonnie October 27, 2025 23:24
@github-actions github-actions bot added unstale A PR that has been marked unstale. It will not get marked stale again if this label is on it. and removed stale The issue is stale. It will be closed within 7 days unless there are further conversation labels Oct 28, 2025
commits.txt Outdated
@@ -0,0 +1,315 @@
[core][cherry-pick] RDT NIXL Limitations + Throw Exception (#58159)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove this file? not related?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oops it was the list of commits for release.. removed now

p
Signed-off-by: kevin <[email protected]>
@khluu khluu requested a review from aslonnie October 28, 2025 08:28
@aslonnie aslonnie added the go add ONLY when ready to merge, run all tests label Oct 28, 2025
@aslonnie aslonnie self-requested a review October 28, 2025 16:00
@aslonnie aslonnie merged commit 9d43d4a into master Oct 28, 2025
7 checks passed
@aslonnie aslonnie deleted the khluu/release_retry branch October 28, 2025 16:47
YoussefEssDS pushed a commit to YoussefEssDS/ray that referenced this pull request Nov 8, 2025
So it can be configured for expensive tests to not retry

---------

Signed-off-by: kevin <[email protected]>
Co-authored-by: Lonnie Liu <[email protected]>
landscapepainter pushed a commit to landscapepainter/ray that referenced this pull request Nov 17, 2025
So it can be configured for expensive tests to not retry

---------

Signed-off-by: kevin <[email protected]>
Co-authored-by: Lonnie Liu <[email protected]>
Aydin-ab pushed a commit to Aydin-ab/ray-aydin that referenced this pull request Nov 19, 2025
So it can be configured for expensive tests to not retry

---------

Signed-off-by: kevin <[email protected]>
Co-authored-by: Lonnie Liu <[email protected]>
Signed-off-by: Aydin Abiar <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core Issues that should be addressed in Ray Core devprod go add ONLY when ready to merge, run all tests release-test release test unstale A PR that has been marked unstale. It will not get marked stale again if this label is on it.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants